Please address the comments from this code review:

## Overall Comments
- Change @Config("case-sensitive-name-matching") to @Config("elasticsearch.case-sensitive-name-matching") so the new setting uses the same prefix as other Elasticsearch connector properties.
- In ElasticsearchQueryRunner you build the config map then immediately create a new variable `newconfig` for the same map; consider building and passing the map in one step to avoid the redundant local.

## Individual Comments

### Comment 1
<location> `presto-elasticsearch/src/main/java/com/facebook/presto/elasticsearch/ElasticsearchConfig.java:59` </location>
<code_context>
     private boolean ignorePublishAddress;
     private boolean verifyHostnames = true;
     private Security security;
+    private boolean caseSensitiveNameMatching;

     @NotNull
</code_context>

<issue_to_address>
**suggestion:** Default value for caseSensitiveNameMatching is not set.

Initialize caseSensitiveNameMatching to false to clarify its default behavior and prevent ambiguity.

```suggestion
    private boolean caseSensitiveNameMatching = false;
```
</issue_to_address>

### Comment 2
<location> `presto-elasticsearch/src/test/java/com/facebook/presto/elasticsearch/TestElasticsearchMixedCaseTest.java:41` </location>
<code_context>
+                .setCaseSensitiveNameMatching(false));
     }

     @Test
</code_context>

<issue_to_address>
**suggestion (testing):** Consider adding negative tests for unsupported index name cases.

Add a test that uses uppercase or mixed-case index names to verify the connector returns a clear error or fails gracefully, ensuring compliance with Elasticsearch's lowercase index name requirement.

```suggestion
    @Test
    public void testUppercaseIndexNameFails() throws Exception
    {
        String invalidIndexName = "TestIndex";
        try {
            // Attempt to create an index with uppercase letters
            client.indices().create(new org.elasticsearch.client.indices.CreateIndexRequest(invalidIndexName), DEFAULT);
            // If no exception, fail the test
            assertTrue(false, "Expected exception for uppercase index name");
        }
        catch (org.elasticsearch.ElasticsearchStatusException e) {
            // Elasticsearch should reject uppercase index names
            assertTrue(e.getMessage().contains("Invalid index name"), "Error message should mention invalid index name");
        }
        catch (Exception e) {
            // Other exceptions may also be thrown, but should indicate invalid index name
            assertTrue(e.getMessage().toLowerCase().contains("invalid") || e.getMessage().toLowerCase().contains("uppercase"), "Error message should mention invalid index name or uppercase");
        }
    }

    @Test
```
</issue_to_address>

### Comment 3
<location> `presto-docs/src/main/sphinx/connector/elasticsearch.rst:55` </location>
<code_context>
 ``elasticsearch.max-http-connections``        Maximum number of persistent HTTP connections to Elasticsearch.
 ``elasticsearch.http-thread-count``           Number of threads handling HTTP connections to Elasticsearch.
 ``elasticsearch.ignore-publish-address``      Whether to ignore the published address and use the configured address.
+``case-sensitive-name-matching``              Enable case sensitive identifier support for schema and column names for the connector.
+                                              When disabled, names are matched case-insensitively using lowercase normalization.
+                                              Default is ``false``.
</code_context>

<issue_to_address>
**nitpick (typo):** Consider hyphenating 'case sensitive' to 'case-sensitive' for grammatical correctness.

As a compound adjective preceding 'identifier support', 'case-sensitive' is the correct form.

```suggestion
``case-sensitive-name-matching``              Enable case-sensitive identifier support for schema and column names for the connector.
```
</issue_to_address>